We are migrating the bug tracker to github Issues. This is now the preferred way to report NASM bugs.

Self-registration is disabled due to spam issue (mail gorcunov@gmail.com or hpa@zytor.com to create an account)

Bug 3392822 - Is it intended that the most recent autoconf release is required?
Summary: Is it intended that the most recent autoconf release is required?
Status: CLOSED WONTFIX
Alias: None
Product: NASM
Classification: Unclassified
Component: Assembler (show other bugs)
Version: 2.16.xx
Hardware: All All
: Medium normal
Assignee: nobody
URL:
Depends on:
Blocks:
 
Reported: 2022-11-21 16:41 PST by E. C. Masloch
Modified: 2022-12-07 10:16 PST (History)
4 users (show)

Obtained from: Built from git using configure
Generated by: ---
Bug category:
Observed for: ---
Regression: ---
Regression since:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description E. C. Masloch 2022-11-21 16:41:23 PST
It is presumably introduced by https://github.com/netwide-assembler/nasm/commit/8453bcfa6c9dd94ab3aad458f11739c491ff27cd and https://github.com/netwide-assembler/nasm/commit/b6151260a1d09a2e98f4d9074080e89fb6b3aa98

I found that trying to set up compilation of 2.16rc10 rejected our server's autoconf 2.69, stating that it requires autoconf 2.71.

I worked around this by downloading the most recent autoconf release from GNU, then setting it up with ./configure --prefix=... && make && make install. From https://ftp.gnu.org/gnu/autoconf/autoconf-2.71.tar.xz
Comment 1 H. Peter Anvin 2022-12-07 10:16:49 PST
Unfortunately this is a bit of damned if you do-damned if you don't kind of thing. I can't easily test with autoconf 2.69, and there are a fair number of differences between 2.69 and 2.71, some of which are highly relevant.

Since the configure script is pre-generated in the source code release files, I opted for 2.71 as it doesn't affect people building the release files.

So yes, it's rather unfortunate but intended.